docs: note the scheduled_at future/30-day window - #24
Merged
Conversation
Document on the TemplateSend/RawSend scheduled_at fields (and the README send example) that the timestamp must be in the future and at most 30 days ahead, matching the hosted API's validation — a past or too-distant value is rejected with 400. Keeps the Python SDK's guidance in parity with the TypeScript SDK. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XCeS6cafCLddV6dakQCKC9
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Parity with the TypeScript SDK: document the hosted API's scheduling window so developers learn the constraint before hitting a
400.Changes
models.py— theTemplateSend.scheduled_atandRawSend.scheduled_atfields now carry a doc comment: the timestamp must be in the future and at most 30 days ahead; a past or too-distant value is rejected with400. Omit to send immediately.send(...)example annotatesscheduled_atwith the future / ≤ 30-days-ahead window.Notes
subject/html"required" guidance from the TypeScript MCP work is already structurally enforced here:EmailContentrequires both, so a text-only email cannot be constructed.🤖 Generated with Claude Code
Generated by Claude Code